Printing system and method of operating same

ABSTRACT

Disclosed herein is a method of operating a printing system including determining a time of a print problem, accessing a database containing a timeline of print-related attribute changes, modifying one or more print-related attributes, and resubmitting print jobs. In another embodiment, a method of operating a printing system involves storing sets of print-related attributes in a settings repository, the stored sets being available for use in processing future print jobs. Corresponding printing systems also are disclosed. The methods and systems can be used to improve the efficiency and/or quality of high volume printing operations.

BACKGROUND

The embodiments disclosed herein relate generally to print production,and more particularly to high volume print production management.

In digital publishing it is important for printers to generate documentsat high throughput rates. When problems occur, such as paper jams ortoner variability, it is necessary to re-run certain print jobs.Furthermore, when a computer that operates printer hardware isreconfigured, output may not meet the necessary qualifications andcertain print jobs may need to be re-run.

Current digital printers are configured to hold and/or resubmit printjobs. A user usually is able to eventually determine what queue orsystem settings were used prior to a printing error or instance of poorimage quality, and to change the print parameters to correct theproblem. However, known systems do not enable print re-runs andcorrections to be made quickly and easily when print-related attributechanges have been made at the system or queue level. It would be usefulto develop a system for quickly re-executing faulty print jobs orreturning to a state of preferred image quality, thereby minimizinglosses in overall throughput rates of a printer due to printingproblems.

SUMMARY

One embodiment described herein is a method of operating a printingsystem, comprising determining a time of a print problem, accessing adatabase containing a timeline of print-related attribute changes,modifying at least one print-related attribute in effect proximate thetime of the print problem, and after modifying, resubmitting print jobs.

In some cases, the timeline includes changes in at least one of printoutput attributes, pre-press attributes, and printer set-up attributes.The print related attributes often include one or both of system levelattributes and queue level attributes. In some cases, print-relatedattributes are saved as part of a set of print-related attributes in asettings repository for future use.

In some cases, the timeline is stored in a memory contained in acomputer at least indirectly operative of printer hardware. In certaincases, the timeline of print-related attribute changes is continuouslyrevised during printer operation and changes are stored in a memory.Sometimes, modifying at least one print-related attribute comprisesreinstating a print-related attribute affecting image quality.

Another embodiment is a method comprising forming a database containinga timeline of print-related attribute changes, determining a time of aprint problem, correcting the print problem after reviewing a portion ofthe timeline proximate the determined time, and resubmitting at leastone print job submitted proximate the determined time.

In certain cases, correcting the print problem includes modifying atleast one of the print-related attributes that was changed proximate thedetermined time. Sometimes, correcting the print problem includeschanging printing conditions without revising print-related attributes.Often, the timeline includes changes in at least one of print outputattributes, pre-press attributes, and printer set-up attributes. Thetimeline can be stored in a memory of a computer that is leastindirectly operative of printing-hardware. In some cases, the methodfurther comprises capturing sets of print-related attributes and storingthe sets in a settings repository for future use.

Another embodiment is a method comprising forming a settings repositoryof print-related attribute sets, at least one set including system levelattributes and queue level attributes. In some cases, the method furtherincludes selecting a print-related attribute set from the settingsrepository and submitting at least one print job with the selectedprint-related attribute set.

Yet another embodiment is a printing system comprising a memorycontaining a timeline of print-related attribute changes, a controlpanel configured to display a selected portion of the timeline basedupon a user request, and a processor configured to receive from thecontrol panel and execute at least one of a modify command to modify aselected print-related attribute in the timeline and a resubmit commandto resubmit jobs submitted after a particular time.

A further embodiment is a printing system comprising a memory containingsets of print-related attributes, at least one set including both systemlevel attributes and queue level attributes, a control panel configuredto display a set of print-related attributes based upon a user request,and a processor configured to use a selected set of attributes inprocessing a print job in response to a user command.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a process flow diagram showing a method of operating aprinting system according to one embodiment.

FIG. 2 is a process flow diagram showing a method of operating aprinting system according to another embodiment.

FIG. 3 is a process flow diagram showing an embodiment in whichprint-related attribute sets are stored for future use.

FIG. 4 depicts an exemplary printing system that can be used for themethods described in FIGS. 1-3.

FIG. 5 shows an example of a screen display for an embodiment in whichprint-related attribute changes are captured in a timeline.

FIG. 6 provides an exemplary screen display showing a window with undo,revert to state and capture state commands.

FIG. 7 shows an exemplary screen display for selecting jobs forresubmission.

FIG. 8 shows an exemplary screen display for selecting particular jobsfor resubmission.

DETAILED DESCRIPTION OF THE INVENTION

Using the print configuration management system disclosed herein,changes that are made to a printing system that affect output, includingsystem, queue and optionally also job level changes, are captured andstored in a timeline or other type of database in order that they can bequickly modified or recalled if desired at a later time. In oneembodiment, the system improves print shop efficiency by allowing forthe automatic correction of printing problems and the automatic re-runof faulty print jobs based upon minimal input from the operator. Inanother embodiment, the system keeps track of settings for multiple,related jobs that are printed. These may, for example, be multiple printjobs for a particular client, or multiple runs of one print job duringexploratory use of a machine, such as a color image, using slightlydifferent settings. For example, when multiple jobs are to be printedfor a client, the preferred group of settings for the client can becaptured and stored in a settings repository or another suitablelocation from which it can be conveniently recalled when the clientrequests a new print job at a later time. When multiple variations of aparticular job are being run, the best group of settings can bedetermined, then captured, and optionally stored in a settingsrepository or another suitable location. This group of settings can thenbe conveniently selected for future print jobs. For example, withmultiple variations of a print job in hand, a print shop may decide, forexample, they prefer the output of the second job they printed. They canthen look at a configuration management panel to determine what settingswere used for the second job and return to those settings such as byundoing all subsequent changes or reverting to a particular set ofattributes.

In one embodiment, print-related attribute changes, including those atthe system and queue level, are captured with a time and date stamp, andthe previous state of the changed settings is kept in memory to allowfor reinstatement of earlier settings. This can be useful if printingproblems occur in order to solve the problems by undoing particularsetting changes. Reinstatement can take place, for example, as a resultof execution of an undo command in connection with a particular printparameter or a set of print parameters. One disclosed embodimentprovides for the automatic reprint of jobs printed during a period whenthe system was not printing as desired.

A “printing system” as used herein includes hardware and softwareaspects, such as a computer-based control system operative of printinghardware, such hardware possibly including xerographic, ink-jet, offset,or other marking technologies, or combination of technologies. A “timeof a print problem” refers herein to an approximate time at which faultyprinting commenced or an approximate timespan during which faultyprinting took place. As used herein, a “timeline” refers to a databasethat can be arranged by date and time. A “print-related attribute”refers to a system level or queue level attribute in a systemconfiguration that relates to printing, including but not limited tosecurity level, color, font, caching, priority, etc. The print-relatedattributes also optionally include job level attributes. A“print-related attribute change” is a change from one print-relatedattribute to another, an addition of a new print-related attribute, orthe removal of a print-related attribute. “Undo” refers to the act of orability to modify any previously made command, attribute, or set ofattributes.

The term “document” is used to denote a document in any state, including(but not limited to) when viewed on a computer display, when formattedas a print file ready for printing, and when in hardcopy form. The statethe document is in at any point in the description depends on thecontext. Also, a “document” may include text, graphics or mixedrepresentations. “Files” are documents or other stored sets of data. Forthe purposes of discussion herein, the term “printer” as used hereinshall include all different types of printer and output devices, bothhard (physical printer) and soft (Web server), or other hardcopy ordocument rendering apparatus and devices.

Referring to the figures and first to FIG. 1, a process flow diagram isshown for one embodiment and is designated as 10. In this embodiment,when a print problem such as a printing error or unsatisfactory imagequality is detected, the approximate time that the print problemcommenced is determined at 12. Examples of printing errors would bethose resulting from the use of the wrong media, a paper jam, tonervariability, etc. Examples of unsatisfactory image quality would beincorrect colors, insufficient resolution, undesired darkness orlightness, and any of a number of other visual defects. The printproblem can be determined by examining output and/or by detecting aprint error at a computer that is at least indirectly operative ofprinting hardware.

A database containing records of print-related attribute changes is thenaccessed at 14. Typically, this database is a stored timeline ofprint-related attribute changes that have been made. Each time entry inthe database has a set of associated data including the identity of theattribute change that was made, and optionally also the identity of theprevious corresponding attribute. The database usually includes systemand queue level changes that affect print output, and often alsoincludes print job level changes. By maintaining information aboutcurrent and prior print-related settings in this way, after the operatorhas reviewed attribute changes they can, if necessary, modify selectedattributes at 16 in order to correct print-related settings. In somecases, modifying involves undoing an individual attribute change or aset of attribute changes that were all made at approximately the sametime or within a certain time period, such as all changes made after acertain time. A set of attribute changes can be undone as a group in asingle step. In one embodiment, selections at the user interfacecorrespond to specific groups of attributes and arguments that make up asystem or queue level change. Each change queries the attribute changelibrary or database to gather the data and invoke the changes throughoutthe software upon selection. In some cases, each system or queue elementhas an attribute dictionary or configuration file that can be updatedupon such desired changes.

Once the desired print-related attributes have been determined and thedata has been automatically transferred to the appropriate locations inthe printing software system, the faulty print jobs are thenresubmitted, or new print jobs are submitted, at 18. In some cases,after reviewing records of print-related attribute changes at 14, adetermination will be made that no modification of attributes isrequired and the faulty print jobs are then resubmitted, or new printjobs are sent, at 18 after any other necessary corrections to theprinting system are made. In some cases, the print jobs that need to beresubmitted can be selected from a listed display of print jobs.Alternatively, a specific time can be selected or entered, and all jobsexecuted after that time can be resubmitted.

In the embodiment shown in the process flow diagram of FIG. 2, generallydesignated as 22, print jobs are resubmitted without undoing particularattributes. A database containing a timeline of print-related attributechanges is formed at 24 and is stored in the system's memory. Typically,this database contains information about the set of print-relatedattributes currently in use during a particular time period on aparticular printer, as well as the corresponding, previously used,print-related attributes. A single database can be used to track printparameter changes for an individual printer or a plurality of differentprinters. When a print problem is detected, the time of the problem isdetermined at 26. The print problem is corrected at 28, and the faultyprint jobs are resubmitted at 30.

Referring to FIG. 3, a process flow diagram is shown for the reuse of astored set of print-related attributes. The overall process isdesignated as 32. A database of print related attribute sets, one ormore of which include both system level attributes and queue levelattributes, is formed at 34. Later, a particular print-related attributeset is selected at 35 and is then utilized in conjunction with thesubmission of a particular print job at 36.

Referring to FIG. 4, a printing system in accordance with one embodimentis shown. The printing system 37 includes a processor 38 and a memory 39containing a print-related attribute database 40. Usually, the databasecontains records of attribute changes. The print-related attributechanges are usually capable of being arranged in a timeline. In somecases, the memory 39 also includes a settings repository 41 containingsets of print-related attributes. The attributes in a particular set areintended to be used together. One or more of the sets in the settingsrepository 41 include both system level attributes and queue levelattributes, and job level attributes optionally can be included. Acontrol panel 42, which often includes a display panel, a keyboard and amouse, enables an operator to review attribute changes, modify attributechanges, and resubmit faulty print jobs. Furthermore, the control paneloften enables an operator to retrieve a particular set of attributesfrom the settings repository or the timeline for use. One or more outputdevices 44 are connected to the processor.

In some embodiments, a selected portion of the print-related attributedatabase 40 is shown on the display of the control panel 42 based upon auser request. The processor 38 receives commands from the control panel42 to undo or otherwise modify certain print attributes and/or toresubmit certain print jobs to the output device 44. In certainembodiments, the processor 38 receives commands from the control panel42 to retrieve a selected set of print-related attributes from thesettings repository 41. The control panel 42, processor 38 and memory 39may be part of a computer that is at least indirectly operative ofprinting hardware, such as a digital front end of a printer, or can bepart of a workflow management system that is connected to multipleoutput devices.

FIG. 5 shows an exemplary screen shot 50 that appears on a display of acontrol panel. The screen shot 50 shows a list 52 of the dates and timeswithin a specified period in which one or more print-related attributechanges were made. The level of the change or changes is displayed at54. To view additional information, the operator selects a particularline entry. This opens a context menu 55 that gives the user the optionsof choosing to review the changed attributes associated with the time at56, review all attributes in effect at the selected time at 57, or savethe attributes in effect at the selected time in a settings repositoryby selecting “save systems setting snapshot” at 58. Another shortcutoption or menu 55 is to resubmit all jobs submitted after the selectedtime. This shortcut is effected by selecting box 59, which states“Select Jobs Since Attribute Change.” The context menu can be accessed,for example, by right-clicking on a particular line entry on screendisplay 50.

Another window that can be accessed from the display shown in FIG. 5 isshown in FIG. 6. This window can be accessed, for example, by leftclicking on a line entry on the display of FIG. 5. The window shown inFIG. 6, designated as 60, displays certain print-related attributes thatwere in place at the selected time as well as the previous correspondingattributes. This window would be useful, for example, if a print shopwants to adjust settings and compare several different versions of aclient's job. With multiple jobs in hand, the print shop may decide, forexample, they prefer the output of the second job they printed. They canthen look at a configuration management panel to determine what settingsthey had for the second job and return to those settings such as byundoing all subsequent changes or reverting to a particular set ofattributes. Furthermore, they can save the selected set of attributes inthe settings repository.

On the display shown in FIG. 6, an operator can highlight a particularline entry to access a context menu 62 (such as by using a right-click)that includes the commands “undo” at 64, “revert to state” at 68 and“capture state” at 69. By selecting undo, the operator modifies acurrent attribute such as by reinstating a previous value of aparticular print-related attribute, such as default font, color sourceprofile, security level, PDF caching, or tone reproduction curve.Optionally, each menu or screen can indicate job IDs printed at aparticular instance of system configuration and a selection in thiscolumn or top level menu will bring up a similar listing of jobs toreprint. The user can then either select particular jobs (per row) or aparticular job plus all subsequent jobs. By selecting revert to state at68, the operator automatically undoes all print-related attributes thatwere made from a designated time forward. In certain cases, some ofthese attributes, such as PDF caching, can be accessed at either morethan one level, such as either the queue level or the system level,while other attributes only can be accessed at a single level. Byselecting “capture state”, the operator captures a set of all settingsin effect at the highlighted time for storage in the settingsrepository.

FIG. 7 shows a screen display, designated as 76, that can be accessed byselecting button 74, “Select Jobs to Resubmit,” on the display shown inFIG. 5. The screen display at 76 provides the user with an option toresubmit all jobs submitted within the last hour by selecting resubmitbutton 78. Jobs submitted within the last several hours can be selectedby entering a number of hours in box 80 and then subsequently selectingresubmit button 82. Jobs submitted within the last hour can be displayedby selecting “+” in box 94. Jobs submitted within a previous period ofhours can be displayed by entering a number of hours in box 80 andselecting “+” in box 94. Jobs submitted within the last day can bedisplayed by selecting “+” in box 84. Jobs submitted within the lastweek can be displayed by selecting the “+” in box 86, and a selectedrange of jobs can be displayed by filling in the desired dates in boxes88 and 90 and then selecting the “+” in box 92. Based on the resultingdisplay, the user can select which jobs are to be resubmitted.

If the user does not want to resubmit all jobs within the last one ormore hours the “+” in box 94 or 96 can be selected to bring up a list ofall jobs within a designated period. A non-limiting example of a displaythat can be obtained by selecting “+” at 94 is shown in FIG. 8, and isdesignated as 100. In the embodiment that is shown, a set of “X” marksappear in the left column at 102. The operator can individually deselector select entries for resubmission. In some cases, for convenience, a“Select All” option is included at 104 and a “Deselect All” option isincluded at 106. After the appropriate jobs have been selected forresubmission, the operator selects button 108 in order to resubmit theselected jobs.

It will be appreciated that various of the above-disclosed and otherfeatures and functions, or alternative thereof, may be desirablycombined into many other different systems or application. Variouspresently unforeseen or unanticipated alternatives, modifications,variation, or improvements therein may be subsequently made by thoseskilled in the art which are also intended to be encompassed by thefollowing claims.

1. A method of operating a printing system, comprising: forming a database containing a timeline of print-related attribute changes, determining a time of a print problem, accessing a database containing a timeline of print-related attribute changes, reviewing a portion of the timeline of print related attribute changes proximate the determined time of the print problem, modifying at least one print-related attribute in effect proximate the time of the print problem, and after modifying, resubmitting print jobs.
 2. The method of claim 1, wherein the timeline includes changes in at least one of print output attributes, pre-press attributes, and printer set-up attributes.
 3. The method of claim 1, wherein the at least one print-related attribute includes a system level attribute.
 4. The method of claim 1, wherein the at least one print-related attribute includes a queue level attribute.
 5. The method of claim 1, wherein the at least one print-related attribute includes at least one system level attribute and at least one queue level attribute.
 6. The method of claim 5, wherein the modified print-related attributes are saved as part of a set of print-related attributes in a settings repository for future use.
 7. The method of claim 5, wherein the timeline is stored in a memory of a computer at least indirectly operative of printing hardware.
 8. The method of claim 5, further comprising capturing sets of print-related attributes and storing the sets in a settings repository for future use.
 9. The method of claim 1, wherein the timeline is stored in a memory contained in a computer at least indirectly operative of printer hardware.
 10. The method of claim 1, further comprising continuously revising the timeline of print-related attribute changes during printer operation and storing changes in a memory.
 11. The method of claim 10, wherein the timeline includes changes in at least one of print output attributes, pre-press attributes, and printer set-up attributes.
 12. The method of claim 1, wherein modifying comprises reinstating a prior print-related attribute affecting image quality.
 13. The method of claim 1, wherein modifying at least one print-related attribute comprises modifying a print-related attribute that was changed proximate the determined time of the print problem.
 14. The method of claim 13, further comprising capturing sets of print-related attributes and storing the sets in a settings repository.
 15. The method of claim 14, wherein the sets of print-related attributes include both system level attributes and queue level attributes.
 16. The method of claim 1, wherein modifying at least one print-related attribute comprises changing printing conditions without revising print-related attributes.
 17. A method comprising forming a settings repository of print-related attribute sets, at least one set including job level attributes, at least one system level attribute selected from the group consisting of font, security level, caching and tone reproduction curve, and at least one queue level attribute selected from the group consisting of color, caching and priority, selecting a print-related attribute set from the settings repository, and submitting at least one print job with the selected print-related attribute set. 